I don't think we create a datasource component. You might be forced to fall back on EJB3 injection. For example:
@Resource(name="jdbc/whatever", mappedName="java:/DefaultDS") private javax.sql.DataSource ds;
Right, but EJB3 injection is just perfect here, no need for anything new, I guess...
Of course, it would be -totally- trivial to create a manager component for a datasource, but I don't see the need.