They don't use cryptographic timestamps with their signatures ?
The certificate might now be invalid, but the signatures were done at a time when it was valid...
There is a possibility that Mozilla implemented their backwards code-signing model on purpose — for example, it allows them to oust unwanted extensions without explicitly recalling their certificates. But personally I think that they just didn't give the matter enough thought.