I found out while doing the classloader changes that the install action
was not unwinding properly if one of the
<install/>
operations failed.
This left the bean in the **ERROR** state but it was still installed in the registry.
This was easy to fix. What is not so easy to fix is determining what
<uninstall/>
operations need to be run to reverse what is already done.
The install/uninstall aren't necessarily symmetic.
For now, I've done a belt and braces job. I run all the unintalls and ignore any errors.