Works around reactiveui/ReactiveUI#661

A workaround for #661, I don't find it a very desirable fix, and I do question if using the WeakEvent pattern as a publisher of events is actually appropriate at all given varying consumers and loosing parity with other implementations (although I wish it was :))