Memory leak and DirectGui

This will sound crazy, but some experimentation shows that it has to do with the fact that you’re changing the name on the DirectEntry. If you change the name on the node, you have to explicitly store it and call destroy() when you are done with it. Otherwise, they don’t seem to leak.

Also, you need to store the DirectOptionMenu and call destroy() on it. There must be some circular reference going on with it.