Ashley
1) load 100mb of images on startup
2) draw them in to Paster (which only uses ~16mb)
3) (the request) release the 100mb of images
at point 3. after releasing all 100mb of images same time I'm removing every instance of every object I don't need anymore. So after a "clean up" there should be only one object in the layout - Paster, and this layout should use only ~16mb altogether because there is nothing else.
i do not say that device can't handle this or there are crashes of any kind.
As I see it. There are hundreds of different kind of objects in the layout, that are using ~100mb in textures. And they are doing nothing. No tests, no collisions. They are simply a "background image". But they take quite a lot of memory and probably quite few draw calls and some CPU just for being there. So instead of keeping them I could exchange them for only one object that takes less of everything.
And this goes only for my example. There a lot of other things that could benefit from ability of dynamic unloading from memory.