Similar (I assume) bug I've been able to replicate, involving global active objects and behaviours
1. - Create an active object on Frame 1 and make it global (same name and type)
2. - Create a new frame in the same application (Frame 2)
3. - Copy & Paste the global object from Frame 1 to Frame 2
4. - In Frame 1, add a behaviour to the active object - an empty 'Always' condition with no actions is fine
5. - Return to Frame 2 and copy and paste the active object - it seems to clone the object instead of duplicating it. It will also rename the global object in the original Frame 1If you save, close and reopen before step 5, the issue doesn't happen. This doesn't happen too if you create a new behaviour but don't add any events to it
Glad you mentioned this because I thought I was loosing my mind. X)