Optimizations on loading and saving of the configuration files opened a loophole
where the user could have no bean tree of the current sun-ejb-jar.xml or
sun-application.xml file available when creating a new child bean (e.g. session
bean or adding a module to an ear).  Child beans didn't pass in a parser for the
proper sun-xxx.xml file because it was expected they didn't need one.

This problem manifested as the message "SEVERE: Missing parser" on the console
window.  Steps to reproduce are something like "create ejb project, restart ide,
add session bean to project".

This hole is easily patched by having child beans pass in a non-null parser
during the load sequence that is retrieved from the root DConfigBean of whatever
tree they are in (this means that common child beans pass in the correct parser
regardless of what bean they are child of).