Hello,
Concerning your problem, when programming on network, there should not be direct reference between objects in the server and client sides unless you clearly mention it (and in fact, if feasible - and i m not sure of it in JAVA at least- I don't see the usefulness of such a thing in this case...)
In your case, you must keep in mind that JAVA uses a garbage collector so it s sometime difficult to determine when the memory is effectively cleared... And maybe your problem doesn t concern memory allocation. A piece of code concerning the client and server communication methods (and also your method to delete World) could help understand what your problem is.
Manu
PS: i m also unsecure about the fact of having a World object on the server side if your topology is a classical server <--> clients. Why not just having the World object on the client side and sending updates of the game/application logic as processed by the server side in order to create/delete/update objects in the world of the clients side? In general, the 3D environment is rendered only on the client side. But maybe your application has some specificities that needs it also on the server side. Hope this helps :?
