Calling TearOff then Destroy on an actor results in client actor also being destroyed

When calling TearOff followed immediately by Destroy, the channel will be closed with the reason that the actor was destroyed, so the actor will be destroyed on the client as well.
In the UDN linked where this issue was brought up, the licensee has included a potential fix.

On the server, call TearOff() then Destroy() on a replicated actor.

Expected: The actor is no longer replicated, so the actor is only destroyed on the server.

Actual: The destroy is still replicated to the client, and the actor is destroyed on both.