Unlikely. The current theory is that those issues have something to do with accessing storage in certain situations on some units.
What happens here is that your apps close... none of your background apps stay cached in memory and switching in Recents will always cause a complete relaunch. The most obvious symptom of a memory problem is homescreen redraws. Your launcher is an app, just like anything else running on your system. But it also is a high priority one, so it Android will only close it out if it is absolutely slammed as far as memory usage goes and it only has enough space for the active application.
Eventually, what you'd see is that a launched app will close almost immediatly, even if it is active. I saw this on my wife's Nexus 5 when it was at 5.0 (it hasn't done this since I loaded 5.0.1 by the way).
I also see no indication that this affects the Nexus 6. It appears to be mostly 4,5 and 7 users. And I have yet to see any memory bleeds on mine, but I'm fussing with stuff so I'm typically not up for a week... but I'm two days of uptime in now and system is at 547MB. I have never once ran into any kind of behavior that would indication a memory leak on my 6 since I got it a month ago.
Incidently, I DID see some reboots earlier on when I was running 5.0 stock. But I'm kicking a 5.0.2 custom AOSP-based ROM and kernel (Dirty Unicorns) at the moment and haven't had any resets in quite a while (DU has been rock solid steady)