Well, I was getting more at the fact that Java encourages lazy habits in part because of its garbage collector. That is, just recklessly nulling out or re-referencing a pointer that may have previously referenced some gigantic data structure. That automated GC at runtime will save the day, but man, what a bad habit it is that people rely on it.
That's not to say that garbage collection is bad, especially if you're already writing in your own solutions to destroy objects. The difference is, you're consciously aware of what you're doing, and more in tune with what exactly is going on inside your computer when the code is being executed.
Your code probably could run circles around mine, but I'll only call you a sissy to your face if you call me an 'armature' to mine!