Default collision profile is effected by previously set profiles

During play:

Switching from a defined collision profile to the default profile results in default behaving as the previous profile. Switching from this to the custom collision profile results in the mesh's default responses being used, but the object type is still the one set by the previous profile.

Switching from the custom collision profile to the default profile results in default behaving as however the custom was set. Going from this back to custom changes nothing.

The expected behavior is when the default collision profile is set, the collision should be the same as the profile set in PhAT for the mesh.