This affects the chmod utility and other GNV components that create files and directories.
A Posix file protection mask does not contain a delete bit. The VMS CRTL sets the delete bit based on the write access bit for the file.
A more accurate Posix behavior would be to set the delete bit based on write permission bit for the for the parent directory. This would have to be done on all operations that create files/directories, or change the protection. It is also more complexity.
Or the rm/rmdir utility could implement the Perl solution, which if the delete fails, to attempt to add a ACE to the file that gives delete permission and then retry the delete operation. If the delete operation still fails, the ACE is removed.
This shows up in some configure scripts, and can be worked around by exporting a symbol to skip that test.