Svcadm disable in global zone affects same service in ngz

I have a service that resides in both the global and non global zones. When I disable the service in the global zone, a svcs -p on that service shows the process name and ID of the svcadmd for the non global. An svcs -l on the service in the global shows online with an intended state of disabled. I have to shutdown the non globals, disable the svc on the global again, enable it, then boot the ngz to fix.
Can I configure the global svc to not "see" the non global processes.

Update, found that I can kill the zone add processes which disassociates the ngz processes from my svc and allows my svc to operate normally. I just have to issue zoneadm -z zone boot to reestablish the zoneadmd for each zone.

Still need to configure my svc in the global to not be affeted by the ngz svc processes.