Sounds like you've modified the classpath
instead of putting your classes in
server/[config]/deploy or server/[config]/lib
Nope the classpath is the same.
Some of the Mbeans that give the error messages are in server/[config]/deploy contained within an sar.
server/[config]/lib only contains jboss jars currently.
It just seems bizarre and shouldn't be happening unless there's some class loader issue.
Thanks. After digging a little deeper I found that 99.9% of the classes in question are in the deploy or lib directory.
There is one wrapper class that extends ServiceMBeanSupport. This class happens to be in the classpath rather than the individual jars. This is simply for code reuse and package simplification.
By moving this class into each of the jars/sars/ears in question the problem is resolved.