Orphaned Swift object with reference to itself not being deallocated

Question

I\'ve come across something I\'ve not seen before which appears different than the regular retain cycle issues that are usually mentioned with regards to closures in Swift a