We have noticed that trees with a large number of items (or deeply nested trees) consume a large amount of memory. We use external dataSources that are passed via the tree's options.

After the tree is destroyed, only a small amount of memory is freed. The rest stays allocated. Recreating the tree several times adds additional allocated memory that never becomes available again.

As far as we've seen, the dataSource itself does not offer a destroy() method or anything similar to free its resources. Is there anything we need to do to destroy the dataSource?