Whenever a MC bean is installed with a jndi: dependency the JNDIKernelRegistryPlugin is called each time a subsequent MC bean changes state. Since the JNDIKernelRegistryPlugin does a naming lookup these calls are expensive to make. Thus the whole installation of these MC beans becomes a very slow affair.

Removing the JNDIKernelRegistryPlugin and any jndi: dependency will remove that burden.

From an user perspective this is encountered on certain EJB deployments which slow down to a crawl.