It is difficult to work with containers if they all need names.
For an example see the method #addTextField here: http://www.avoka.com/click-examples/source-viewer.htm?filename=WEB-INF/classes/net/sf/click/examples/control/html/cssform/ContactDetailsForm.java
If names are mandatory one will have to define a name for each ListItem and FeedbackBorder. Defining names in this context only adds overhead that won't be used.
I can see three use cases for defining a name:
#1 bindRequestValue - Fields still require name to be defined as per AbstractContainer#insert implementation
#2 Velocity templates - if one needs to reference the Control inside Velocity a name still needs be defined.
#3 Lookup controls inside Containers - again a name should be defined if one needs to do the lookup.