LzDatapointer, LzDatapath and co. leak memory, because there is no update of their "context"- and "__LZtracking"-member when the referenced datasets has been destroyed.

To minimize this memory-leak, we should clear out the "childNodes"-member of LzDataset in the "destroy"-method of LzDataset by calling "setChildNodes([ ]).
This approach of setting "childNodes" to an empty Array has got the advantage of updating any data-bound view, compared with simply setting "this.childNodes=null".


Still open:
- Even if the proposed approach minimizes leakage, it does not completely provide a mechanism to stop this misconception! => What about creating a handler to the "ondestroy"-event of the context (if it is an instance of LzDataset), so we can clear the leaking members? This should solve this memory-leak issue.

- How to rebind datapaths? => whenever a new datasets with the same name has been created, how shell we handle databinding?