Ah, maybe I was wrong - and it actually is probably more useful that way anyway. If you create an object at runtime then you might create it again later even after destroying it, so keeping its textures loaded helps prevent jank on the next creation.
Weeell not necessarily xD
Action to unload object would be really nice.
Scenario of how this could be useful. I was struggling with this for mobile games
You have a background made from 20 different objects and a lot of instances of them (tilemaps, tileddbg and sprites), and then on start of the layout you could simply paste all this objects into a Paster plugin and destroy/unload those objects because you don't need them anymore for this layout.
So instead of ending up with a bunch of different objects you have only one object that uses less memory and is easier to manipulate.
From my tests 1 sprite with few animations, each one have four frames with big images takes about 50mb of image memory.
After adding a Paster and pasting all of this sprites memory goes to about 60-65mb - Paster+current sprite loaded into a memory.
15mb or even 30mb instead of 50mb it's quite a lot for mobiles
Please consider adding an option to unload objects from memory, pretty please ^^