>Can we have an array of all vars before instantiating an object and after that? But even if we do have such array, how will we know in which order we need to release our objects?

Release the remote descendants first and move back up the geneology. Remove "adam and eve" last is a good rule of thumb.

>
>If the above scenario is true (object instantiates other objects and sets reference to itself to these objects), then it's a huge design flow. It should not do that.

That is weird. It seems like a "circular reference" by design. But why. Any object instanciated would offer a "parent" path back to the "super" object.

I notice you're in New York and working with MM. Are you, by chance, working on a health management or state employee benefits system?

Frameworks cramp my style and the paradigm:0). Good thing they got you!