The ConfigurationMonitorGBean maintains a cache of active configuration class loaders and when a configuration is shutdown, it tells the openjpa PCRegistry to remove any cached classes associated with that class loader. This won't work any more because there is no such thing as a configuration class loader. It might be possible to get the bundle for the class loader, then request the list of managed classes and iterate through the classes looking for any class that might be defined using a BundleReference class loader for that bundle. If one is found, then that classloader can be used for the deregister() operation.
For now, the insertion of the map entries is disabled.