See my comment below; Mozilla has been well aware of memory fragmentation for years and has been constantly working to decrease it.
Could explain their recent flurries of rewriting the javascript jits.
[1]: https://www.ohloh.net/p/firefox/analyses/latest [2]: http://www.ohloh.net/p/chrome/analyses/latest
I hope they get it sorted out because it is the main blocker to getting a lot of the early adopter crowd who have switched to chrome back onto Firefox.
Also, I have flash disabled, and use 3 separate builds of chrome on OS X to separate web accounts, dev instances and anonymous browsing