I have found this on all browsers tested - IE, Firefox, Chrome and Safari on Window sand Safari on Apple.
So what's the deal here? On small apps it isn't noticed, but for large WebGL apps like mine (orbitingeden.com) this is a real issue and my users are going to think the software is even more of a resource hog than it really is. The following image shows these refreshes gobbling up all of my available memory, so garbage collection is not working and / or JS and DOM objects are not being released:
Does someone know of a trick to force the browser to do a true dump of memory? Why is all the documentation out there wrong?