Hmm... technically I don't see why setting a NOT NULL constraint to a foreign key should be considered "breaking the foreign key reference".
You're not touching the data here, but only the constraint definition.
About the error message with the DROP CONTRAINT command: looks like a bug to me as well.
I recommend to have a support incident opened for that.
- Lars