A quick reply as I’m currently away from the office…
The design of the configuration system was not intended such that the ComponentManager is used as a central lookup object during runtime. Instead, most of the time, you should only use the component manager to register things with during setup.
So, during initialisation, you create a component Foo and register it. Then, when you want to create component Bar that depends on Foo, you inject it in using the Joda-Bean injection method and the INI file ::foo reference. ie, you do not go to the manager and look it up. Note that this is different to how you work with the context in Spring!
This way, the principal usage of the manager is during setup - only low level framework tools (like the RESTful code) use the manager after setup. This results in less coupling between components and forces you as a developer to think more clearly about your components and their dependencies, and also externalises that knowledge into the INI file (rather than being hard coded into a Java based manager lookup).
Having said all that, it should be possible to use a static method on ComponentManager to access the manager at any point in the application. We just don’t recommend that approach.