Memory profiling shows that we have more than 50
org.apache.xerces.parsers.SAXParser instances
allocated on heap while the app is running. They
are useless and can be released. PropertyHandlers
in o.n.c.windows.persistence hold them together
with some configuration and bunch of other objects
belonging to Xerces. 

If I get it right they are held because the system
uses these handlers for saving of winsys state
during the shutdown. I will attach a patch that
saves the memory and creates new instances of
PropertyHandler-s for saving. The better approach
can be to split loading and saving. I have not
measured impact on startup time. It should be
pretty small as we will collect some object
instead of promoting them.

It should give us some tens of kB (43 instance of
SAXParser, XML11Configuration, a lot of QNames,
some string instances).