Probably, but I fear that tabs are not a good fit for this structure. Tabs are at their best when hosting self-contained “sub-apps” that are independent of one another (such as “menu”, “hours”, “order history”, &c for a restaurant app). I get that it appears initially seductive to wall off different functionality applying to the same business object in tabs - I’ve done this before also, but have found it does not hold up well from a UX perspective, aside from any technical trouble you’ve run into.
Without knowing more about what your business-level domain looks like, I can’t say much more concretely, but generally speaking I think my first instinct would be a breadcrumb summary/detail design, where you have a summary page that is capable of:
- spawning new objects,
- descending into existing ones by navigating to their detail page,
- deleting unwanted objects
I would have the detail page take its notion of what constitutes “the currently focused object” from a service that is injected by both the summary and detail pages. The detail page could have a breadcrumb link back to the summary page (and also, if desired, a “delete this object” button that does the deletion and returns to the summary).
I believe this approach would design away the specific technical problem you’re having, as well as resulting in a more intuitive interface for the user.