Here we go again...
If the vulnerability is limited to SSL 3.0, an easy workaround would be to disable it on both servers and clients.
Most servers should already support at least TLS 1.0. I have been using security.tls.version.min set to 1 on Firefox for a while (which disables SSL 3.0 and below, and also disables the "no extensions" fallback), and other than a period of time when archive.org was SSLv3 only, I have seen no issues.
For clients, a quick look at https://www.ssllabs.com/ssltest/clients.html shows that even older clients (Android 2.3, Java 6, the oldest supported version of IE, etc) support TLS 1.0, so there should be no issues disabling SSLv3 on servers too.