I disagree. Let me give you a situation that comes up regularly in enterprises where you can have an account lockout and nothing intentionally malicious happened.
Audits are being done and the login in question is a known one because of an application. The password is hardcoded (it still happens in 2015) by the application, so the DBA can't change it. If he or she does, the application can no longer connect because you have no option of changing the password in the application. Unfortunately, whoever doing the audit accidentally toggled the brute force switch and before anyone knew what happened, the login was locked out.
Given this scenario, which still happens all too frequently, how would you propose to unlock the SQL Server login and restore access to the application?