It's an unintentional omission, I'm sure. Sometimes it's just hard to track down all vestiges of legacy code.

A patch (untested) has now been submitted. If it's deemed suitable upon review, I'm sure we'll see the appropriate change soon.