These problems did not exist in the web player build of this game so it is specifically WebGL. It's also worth noting that I need to physically close the web browser before the browser decides to release the memory used by the project. If I do NOT refresh the tab my memory stays stable, however. It will never go down and the browser will inevitably crash due to memory overload. I will refresh my game, now it's using 660 K, I refresh my game now it's using 900 K, I refresh my game and now it's over 1 million K. So let's say Firefox is using 480 K after I open my game. If I load up my game in the browser and REFRESH the browser page after the game loads, it will add to the total memory used my browser (in task manager). I can't release many details about my project or rather anything at all but here's the problem: Scene changes don't seem to increase memory.
You can still memory leak if you are rapidly refreshing your browser. Edit - Firefox 52 seems to have smoothed this issue out.
