I can reproduce, but it's a problem with the runtime architecture: triggers fire on object instances, not behaviors, so either behavior can trigger a general "On shoot" condition, which doesn't distinguish between each behavior's triggers.
I think this was reported in another bug a while ago.
I'll leave this report open but given that architectural changes are needed I don't think this is something we'll fix before C3.