Personally, I would either write module that abstracts away the need for a global variable, or at least has a getter function for retrieving it.  Something like

    function foo_get_the_service ()
    {
      static $service;
    
      if (! isset($service)) {
        $service = foo_init_the_service();
      }
    
      return $service;
    }

Several Drupal API functions do something similar (eg, [menu_get_active_trail()][1] and [menu_set_active_trail()][2]);

And then preferably, your module would also have helper functions so you don't need to access the global directly.  If something really does need the global, then you would use the getter.

If your global is an instance of a proper PHP class, then you could look into using a real [singleton][3].

[1]: http://api.drupal.org/api/drupal/includes--menu.inc/function/menu_get_active_trail/6
[2]: http://api.drupal.org/api/drupal/includes--menu.inc/function/menu_set_active_trail/6
[3]: http://stackoverflow.com/questions/203336/creating-the-singleton-design-pattern-in-php5