Thanks Feike, I didn't have the chance to post here, but I also found that workaround, but not only that, but the real cause is the archetype itself.
That is, as you stated the best is not to deploy to the server when creating the project, but creating the server after that.
The message about the Servlet 2.4 API specification is fixed by upgrading the definition in the pom.xml, the same applies to the Java JDK, event the most recent archetype (10) is using JDK 1.6, when in fact, the recommended JDK for AEM is 1.7 or greater, that also must to be updated.
After that, I create a new Server (updating the port numbers too) and add the modules, after all of this being done Eclipse effectively publish to the AEM instance.