There's very little state in DatastoreImpl. There's the write concern, the mapper, and some decoder stuff. If these settings are universal for your application, which is usually the case, then this instance can be shared at the application scope just fine. If you use BasicDAO, then its only state is the entity class it operates on and the Datastore which we've already covered. This would also be generally safe to share.
Generally speaking, most of these components have very little mutable state that would break concurrent access. It's always a good idea to test, but in this case it's a pretty safe thing to do.