Profile - Fields should NOT inherit REQUIRED property of custom fields

Currently, if you create a Profile field (uf_field) which links to a custom field which is REQUIRED - then that field becomes REQUIRED in the Profile form (even though uf_field.is_required is FALSE). This is incorrect behavior. The is_required property for uf_field(s) should behave independently of the linked core or custom field.

To recreate, on Demo... set is_required for Marital Status custom field to TRUE. Now browse to profile 1 (civicrm/profile/edit?gid=1&reset=1). You will see that the Marital Status field is REQUIRED even though this field is NOT marked required in the Profile Field screen.