I am not afraid about BEAST, but I felt it would be wrong to penalize those who have legitimate reasons to be worried. In the end, it's all about context.
That said, perhaps the penalty for using RC4 with TLS 1.1 and better (which are not vulnerable to BEAST) should have been harsher. I'll consider it for a future update.
That still wouldn't help old clients. For them, only one solution: upgrade!
With OpenSSL, the best we can do right now is prioritize suites so that SHA2 ones are on top. By doing that, you know that TLS 1.2 capable clients are going to use good suites. The rest will fall back to whatever is below.
At some point, the world will have to tell them "you're on your own" like it finally did with IE6. Perhaps give them helpful informative messages to upgrade - I bet if Facebook and Twitter redirected old browsers to such a page, their market share would shrink to negligible levels overnight.
I agree with the principal of pushing people towards upgrading, but it's harder if you can't show them a helpful message to explain things.
With regards to BEAST, the problem is that a server has no way of telling if a client implements the mitigation technique. The only 100% safe assumption you can make is that the client negotiating TLS 1.0 is vulnerable.
I use CipherFox (https://addons.mozilla.org/en-US/firefox/addon/cipherfox/) to disable RC4, then only enable it specifically when it is needed as far too many servers not only support it, but attempt to use it when a client still supports non-broken/backdoored algorithms.
Not only is RC4 weak, but it was designed by an RSA Security employee. RSA have proven they can not be trusted, and I think are now on the slow slide into decline and death. Contracts will sustain them for a few years, but they certainly aren't getting any more of those now.
EDIT: actually, SSL Labs stopped requiring server-side BEAST mitigation a month or so before Apple finally handled BEAST in OSX Mavericks. It happened only after I had been satisfied that BEAST exploitation was not very likely. You can find more information here: http://blog.ivanristic.com/2013/09/is-beast-still-a-threat.h...