Discussed this offline a bit, but because the Router injectable listens (indirectly) to location changes, and is not part of the destroy cycle of components when an application is disposed, during tests and multi-app environments it's possible for a route change to trigger a dynamic component loader load into DOM that no longer exists.