Yes, I have begun some work on this and it's looking promising, but that work was set aside for some other stuff. I recently have picked it back up and am hoping to have it in a snapshot build and then in a milestone release within the next couple of weeks. That said, I also am focused on some other work regarding tighter integration with Spring Security and that work has a slightly higher priority. Again, I'm shooting to have both of these ready in the next couple of works, but they're both non-trivial bits of work, so I may only get one of them done in time for a M1 release.
With that said, handling of an expired Facebook token is not a new problem starting on December 5th. It's just a new twist on an existing problem: How do I renew a token (from any provider) when that token is no longer valid (for any reason, including expiration or revocation)? For example, today, prior to December 5th, how would you handle the case where the user revoked your token from Twitter? The general answer is that you must go through the authorization flow again. Facebook doesn't offer refresh tokens and the ONLY way to renew an expired token is to go through the authorization flow again-
and that's the same solution to dealing with a revoked token. I'm not working on a refresh token solution for Facebook, because no such solution is possible-I am working on automatic handling of invalid tokens, regardless of the provider or reason that they're invalid.
So, back to your question: Yes, I am shooting to get something out prior to December 5th, but I am not making any promises.