Comment 7 for bug 1246383

Unless it's a significant pain point somewhere in the API, I'd personally rather live with this as a known issue until 5.6 is prevalent (it's certainly not today), and note it at the API layer (we don't allow user-defined expiration in too many places; where we do allow it, we can claim that expiration may occur earlier than specified, but never later).