Why do retain cycles become non-obvious in modern async architectures?

Indirect ownership chains form across closures, services, and event buses.

Modern apps use coordinators, publishers, reactive streams, and async closures. These create distributed object graphs where object A retains B via closure, B retains C via callback, forming cycles that are not locally visible.