I think it would be well worth studying what the differences are between different open source licenses, so that you can explain to whoever is 'banning' you from using them, what they all mean and what the implications are for your company.
For instance, I would never advocate using a GPL'ed library in one of our closed source programs, but an L-GPL'ed could be made to work. Other licenses are similarly less encumbered.
Also bear in mind that just because a library is published on the web as GPL, quite often, if you email the author(s), you may find that they have other licensing options. For instance I was interested in one GPL library, emailed the author and he said he would be happy to license for closed source projects for $100 per year for support and no runtime cost (that's $100 in total for anyone in our company to use the library on any number products we ship).
This is a damn sight better than $3000 for the development version and $500 per runtime for the commercial library I was also considering. Admittedly the commercial library did much more than the open source library, but we didn't need all that extra functionality at the time.