Yes, if it is something that works in Eclipse but not STS it is certainly a good idea to raise a ticket.
Even if the problem is not in STS itself, raising an STS ticket is a good starting point. Eclipse devs are generally not receptive to tickets unless you can reproduce problem with a plain Eclipse.
Also, before raising a ticket, it is useful to try out a more recent milestone of STS 3.0 based on Eclipse 4.2. Active development now is on 3.0.x based on E4.2 so it is most interesting to know about and fix problems with 3.0.
You can get access to the milestone builds via the official STS downloads page
Click on 'other downloads' to expand the 'hidden stuff' :-)
Then scroll down to find 3.0.0.M3 based on E42.
If you rather wait a little longer, 3.0.0 is in the final RC stages now and will be released shortly (sorry no precise date, maybe a week or so :-).
Last edited by Kris De Volder; Aug 1st, 2012 at 01:37 PM.
Reason: Remove a comment that clearly does not apply to the situation.
Kris De Volder -- SpringSource