If you stick to the laravel what of doing things, ServiceProvider loading can be defered.

If you want a CI like approach, then no there is no such concept of library in laravel, and you want to lazy load librairies on the fly you'll have to do it yourself.

By the way, I don't think it'll be a problem because:

• Loading 10 files don't add too much overhead over the 200+ files laravel load.
• Artisan optimize command can optimize the loading for you in production (check the doc to know how to configure it)
• Install apc and you'll not care anymore about 10 files loaded because they'll stay in memory anyway.

So, no matter you are in production/dev, this isn't really a problem.

By the way, may I recommend you to learn how to work with laravel packages (workbench and composer) instead of doing it the old CodeIgniter way.