This is the same behaviour as in the desktop Architect. There are cases where you want to create a new element in a different place than the active package. The creation should respect the place you trigger the process from.
When I want to create an entity in a different package, I can do it, that is OK. But is there any case when I may need to create an entity out of all package folders? That is what I am addressing here…
You may want to create a general transformation similar to _copyAll or a general workflow used for closing modal dialogs that you want to access from all packages. Also when you trigger the action from a group one or more levels under your package folder it would have to be determined first if you are in the active package and then determine that you probably want to create the element on this level and not on the package level. I think the approach that the active (trigger) place is where you want the new element placed rather straightforward.