Major Description
We've recently made a change to AbstractServiceRegistryContext so that it gets passed a BundleContext on construction and caches it. This creates problems down the line because utility bundles will end up using their own bundle context for lookups instead of the context of the calling bundle. I've seen this behaviour in calls to ServiceHelper.findService().