The name of the configuration and its contents are two seperate things. You can choose to call the installed configuration whatever you want, and that configuration can contain what ever you want. The default configuration name is "default" as otherwise, even with a single configuration you would have to run with a "-c the-name-i-used-during-install" to launch the configuration.
I see, the configuration provided with the JBoss installer can have whatever name you like.
Now when I choose to install the ejb3 installation with whatever name I like (e.g. EJB3) by using the installer. Do I get the same configuration as I would have by downloading a ZIP archive and starting JBoss with the -c all option?
I would like to have an EJB3 enabled configuration providing me all the same services as e.g. a jboss4.0.3/server/all configuration provided with the normal download. Thus providing everything like farm deployment, clustering, mail services, etc...
The all configuration should be similar, but it won't be exactly the same as the installer allows for an arbitrary selection of the components in the zip dist all configuration. This requires that services be broken up along the lines of installable features with dependencies.