Galeon's feature of using an existing process instead of starting a new one
is a little too promiscuous when remote X connections are being used.  This
is best demonstrated with an example:

(assuming galeon is not already running)
DISPLAY=localhost:0 galeon www.gnome.org &
DISPLAY=remote:2 galeon galeon.sourceforge.net &

Will cause both pages to appear on the local display, which is clearly not
the intended effect of the commands.

I am not sure whether this is a bug in galeon, or in one of the underlying
gnome libraries.  Either way, the fix seems to be to query the existing
process first to see if its DISPLAY is equivilent to that of the new
fledgeling process, and launch a new galeon process if not.