The SSL thing shouldn't affect anything with Facebook Connect functionality when using it on a site, to my knowledge. The SSL requirement is required for Canvas apps, which are displayed on Facebook.com through an iFrame. This is simply to prevent 'sniffing' of user data when at a coffee shop or other open places. Facebook Connect (at least how JFBConnect does it), is already secure because:
1) The login pop-up from Facebook is already over SSL
2) They assign a cookie to the user which
3) JFBConnect verifies over an SSL connection from the site's server, not from the user's browser. The server just has to be able to make SSL requests, it does not need an SSL cert of it's own.
Finally, yes, there will be some changes to JFBConnect required to use the new OAuth method, which is more secure than the current OAuth method we've implemented right now. This has some extra protection for securing, and verifying, the cookie in step 2 above.
So.. in general, sites that use JFBConnect/Facebook Connect will not need an SSL cert unless they want to display their site on a Facebook.com page.
Keep the questions coming. We're always going over this stuff too to make sure we understand the changes, since if we don't implement something right, there's a lot of unhappy users. If you see anything you think we should know about it, always ask or let us know!