The field authData does not actually exist in the DB, it is synthesized from the _auth_data_* fields in the DB, so direct manipulation does not work in all cases.
The correct way to delete authData is to either call ParseUser.unlink or via REST call:
body: {
"authData": {
"facebook": null
}
}
Your expectation seems valid and intuitive, so Parse Server should probably interpret a request to set authData to null correctly as removing all authData entries. You could also try to unset the authData field, not sure if that works.