then go to my office for a lesson in Java memory leaks.
If you have a program that is long-running (that is, it doesn't clear all the objects you created every time a new http request comes in), and you aren't thinking about memory leaks, then you have them.
Recently I saw a case where a guy had written a program half in C and half in Java. It had some leaks in it but he couldn't find them (mainly he had not been using any introspection tools, so it's not surprising. If you want to find leaks, you need to be able to look at what's going on with your memory. Use jmap or something).