Object preserving problems on {"op": "remove"}

[narcoticfresh]

So well.. After #28, #32, #33, here comes the next one in the series to make it all "object safe" ;-)
Sadly our devs only now thought to use the {"op": "remove"}, so this only comes out now ;-/ If I look at the remaining ops, this really should be the last one ;-)

When {"op": "remove"} is used on a hierarchy that leads or contains to empty objects, they are falsely converted from {} to []..

There are even tests that assert this wrong behavior..

Details will be visible in the PR..