Sorry, I meant to say it triggers the SOCKCLOSE event with an error. This feature was implemented/tested around ten years ago. At the time we likely decided that it should trigger the SOCKCLOSE event because the socket was already open and connected at that point. Another design decision was to make it fail gracefully and to not allow the connection to continue insecurely, since the point of requesting STARTTLS is to secure the connection.
