That's the way I'd normally go, load your configuration once during system initialisation and then just pass the hashref/object holding this information around to other modules.

Another way would be to use a Singleton (see for example Class::Singleton or Class:StrongSingleton). You'd still have to use and call the Config module in every other module, but Config would only load the configuration file once and just return the same instance of itself on every other call (note: this will and can not work with forked processes).