MSC services are global, so having them deployed in a jar via service activator will result in every WAR etc being able to see them.
Glancing at the OSGi implementation, they appear to use a nested step with all services created in that steps context which is al added to the SVH. So the completion of that step will block until the core Framework service has completed