I recommend changing the behavior in the new product pricing fields in 1.5 for drop downs, otherwise I believe you'll be swamped with tech support issues from confused users.
If the user defines a product pricing field as a drop down with choices like:
Code assume all answers have a quantity of 1. If you select first choice "none" then in the order confirmation screen and email it displays you purchased quantity 1 of "none".
You really can't use the drop down because there is no way to have an opton for the customer to not purchase the product.
If the price is 0 or blank have code assume a quantity of 0, not 1.
Or build into the drop down list a default "not selected" choice.
I think developers will expect there to be a "not selected" choice because we are use to having that as the first choice in drop downs we create in HTML forms.