Objects that have cached the result of LogManager.getLogger() and are then
copied via the corba copying code will end up with new instances of the
LogManager class, which is expected to be a singleton. When the new instances of
the class are created, the LogManager.<init> also constructs a new Cleaner thread.
The end result is a very large memory leak; this is also at least partly
responsible for the deserialization performance regression we are seeing.