Comment 9 for bug 786418

Im unable to fix this in a short amount of time;

This is a much wider scope problem - we need to clearly define how deletions cascade down -
there are two types of methods that need to be fixed;

.remove() removes the object itself (currently does not cascade, does not maintain relationships)
.remove<ModelClass> (for example UserService.removeUserGameProfile) these remove the relationships of an object related to the one in the service, but do not remove that object itself.