What version of WebSphere are you using?

I had the same problem with 6.1.0.19 (works with 6.1.0.25)

It was able to work around it by just entering the JNDI name instead of browsing for it.