We will investigate further, but can't say much more about this now. We really only include 1 JS file from Facebook. They're including the remaining 8 files, and they could potentially one day include 800 if they wanted too. Obviously, don't think this will be the case
I'll look into adding the 1 file to a DomReady call from mootools, but it may not work there since some of the functions (I believe) need to be run as they're encountered on the page due to the namespace translations that facebook requires (extensions to the html spec with lines like <fb:login-button> </fb:login-button> which actually 'creates' more code on your page).
The inline JS isn't causing any extra http requests, but it's possible we could condense it some more. With the login module, I know it is, but there could be better ways to do it to make sure any JFBConnect code from a page is tidily put in the same spot.