Currently, the schema and the objects remain after the user is dropped, cf. repro2.sh attached.
The authorization id of the schema of the dropped user is still that id (dangling) after DROP.
Perhaps ownership should revert to the DBO when a user is dropped, or should DROP USER do a cascade delete?
There is no way currently to change the ownership of the schema to another user.
At the very least we should document what happens.