Yup, you've found our dirty little secret. In the next release, we're going to have a standalone javascript file which is included. That will prevent echo statements from the library, which, is not the best thing to be doing.
Our best, very easy fix suggestion is to make a quick modification to the following files:
/components/com_jfbconnect/libraries/facebook.php. In the getInstance function, add the loadJavascript parameter:
public static function getInstance($loadJavascript = true)
{
if (!isset(self::$libraryInstance))
{
self::$libraryInstance = new JFBConnectFacebookLibrary($loadJavascript);
Then, in the same file's contructor, change it to:
private function __construct($loadJavascript = true)
...
if ($loadJavascript)
$this->initJavascript();
Finally, in the user plugin (/plugins/user/jfbconnectuser.php) at line 35, change the getInstance call to not load the Javascript:
$jfbcLibrary = JFBConnectFacebookLibrary::getInstance(false);
Test, test, test. It's possible this could cause issues somewhere else, but hopefully not (mainly, when you're logging in, if you don't do a redirect, the JS won't be on the page).
Again, sorry for the troubles. This was planned to be corrected soon, but now that we know of an instance where it's a problem, that jumps it up in the priority.
Thanks, and let us know how the above works out!