yes, you are right: the bean browser only recognizes the beans that are directly available.
(The jars of eclnthotdeploy/lib are taken into the class path for analyzing the beans, but their content is not un-zipped... - we only scan the file structure...)
...background info: we scan for the classes of a package using the classloader. Classloaders cannot be queried... - for packages they return back a file-resource that we then use for querying for *.class files. If a package is in a jar, this does not return any information.
Only way at the moment to make these classes appear: you need to manually register them in dispatcherinfo.xml ...