I don't think that "I like it better" qualifies as particular circumstance where valid reasons exist, since the reason would then apply to your person, not the code base or the project.
I can think of some other examples that justify the SHOULD NOT:
Project depends on some third-party tool, framework, whatever... that relies on names to identify visibility.
Class method names need to mimic those from other project that use such convention (e.g., because it's a port from another language).
Project was started before PHP/5. Renaming would break backwards compatibility.
Thus it isn't strictly forbidden, but it's clearly discouraged; probably, because it provides redundant information that can get on the way on further refactoring and can even be wrong:
// r12345 Expose HTML escaping
public function _escapeHtml(){
}